@ziggurat I got carried away by looking at neofetch and got this

b17c8604-9f05-4eec-b669-034d12abba2a-image.png

It's a bit large though for a 64x80 standard Linux console.

I think I have zeroed-in on the issue (but not solved it yet). The missing puzzle piece was SDL.

Emulationstation is built on top of SDL, which has its own keyboard library. Something is not accounting for modifier keys: either the SDL the way emulationstation is written.
I think there is still hope as the debug log (see end) can see that both Arrow key and Shift and it even shows that my keys are mapped to both down and up in es_input.cfg. Just need to find a way to access that second option in some way.

Anyone has an idea how I can access the second value of my key, or knows their way around emulationstation source so I can add the function myself?

Edit:
I found where F4 is hardcoded for emulation station, which makes me think I can hardcode arrows + shifted arrows in a similar manner. It is not a great solution, but it is something...
The only problem I have is that I don't know how to build my own version of emulation station with the changes if I made a copy to my own github.

Also, I don't know SDL well enough to code it myself. Anyone able to translate my pseudocode into actual SDL and cpp?

IF keydown(shift) AND keydown(down) THEN return up END

Also, happy to hear any other solutions!

@mitu
Ho right, 3rd party! Yes that sound fair.
Ok thanks!

@chuck_b Yes, whenever you update all installed packages or just ES from the setup script.

I would keep a copy of the new ES binary with the remapped quit key and then, after updating, you can overwrite the ES binary with your modded version, unless, of course, there is a new feature in ES that you desire, in which case, you would need to recompile.

@smurf said in Daphne command line not working:

I have lots of space on my sd card so I have a couple versions of each game.

You don't even need the .m2v file in each folder for different rom versions of the same game. Just point the path in the [gamename].txt file to the folder where the .m2v resides. For example, my lair.m2v resides in daphne/lair.daphne, but I also have dle21 in its own directory daphne/dle21.daphne.

My lair.txt in daphne/lair.daphne/:

. 151 lair.m2v

My dle.txt in daphne/dle21.daphne/:

../lair.daphne/ 151 lair.m2v

Mind the first line. In lair.txt, it points to "this directory" (.), but in dle.txt it points to lair.daphne "one level above this directory" (..), both paths seen relatively from the location of the respective .txt file. Since both rom versions use the same video file, this saves a lot of space.

Alternatively, you could create a symbolic link to the file in the other directory:

ln -s /home/pi//RetroPie/roms/daphne/lair.daphne/lair.m2v /home/pi//RetroPie/roms/daphne/dle.daphne/lair.m2v

The first method has the advantage that it still works even if the daphne directory is moved to another location, as long as lair.daphne and dle21.daphne remain at the same relative positions to each other.

Yeah I know, you said that you have lots of space, but maybe that will change in the future with an ever growing games collection, or others here will find this useful. :)

Thanks for the resource, this will definitely be something I'm looking into for another possible project. You are absolutely right about the syncing of two being a problem. As weird as my use case is, I only need one Raspberry (from a kooky angle, the video is being distributed to one/both players). After looking into wedges I think that's the route I'm going to go as I easily have access to USB HID injectors at work/off ebay I can utilize that I didn't realize I could use. Thanks for the link though, I'll definitely be using it.

NIce one, that fixed it!

@wheeliebar overscan_scale=1

@mitu I made it! I have deleted whole scummvm folder, rebooted and the ES finallt works!

Thank you everyone. The problem is officially solved.

@meneer-jansen My pleasure. :)

@mitaholo Three years later and still....nothing. So disappointing that you needed help and someone helped you....but once you had the answer you weren't willing to share it with others having the same problem.

@pbkoning said in Command line for lr-stella:

I guess that lr-stella is started in a config file or something? Where can I add my command line option?

You'll need to alter /opt/retropie/configs/atari2600/emulators.cfg, but remember that the command line options that work for Stella don't necessarily carry over to lr-stella. When you say you already achieved what you wanted on Windows, was that through RetroArch? If it was actually the standalone version of Stella, it too can be installed separately through the RetroPie-Setup and the command line options can still be altered in the file I referenced. Something else to keep in mind is that particular file gets overwritten after every update, so you'll want to make allowances for that.

sorry, but did you hit the Fn button with F4, because MS keyboard works like that.

Found the solution.

Instead to just entering retroarch at the command prompt I needed to enter the full path of the binary or /opt/retropie/emulators/retroarch/bin/retroarch in this case.

If you are already in the /opt/retropie/emulators/retroarch/bin/ directory you need to type ./retroarchto run the command.

@asotocuevas

By turning the power off to a Raspberry Pi (pulling to cord), you stand a good chance of corrupting the SD card. The Pi does not have an off switch. It must be shut down in software using the Linux command line. There are many hardware solutions on the market to provide safe shutdown of the Pi.

However, I use the software feature of Emulationstation in the Quit menu where you can select shutdown. Only then can you turn off the power.

https://retropie.org.uk/forum/topic/11476/turn-off-retropie-safely

Also, your power supply is not powerful enough, you really need at least 2.5A available.

@milesacul Sorry if this topic is becoming spam. Got some progress. If there is no defined install_bin_$id function, you use wget --spider -q "$__binary_url/${__mod_type[$idx]}/${__mod_id[$idx]}.tar.gz" to try to pull the binary. For now, I will check if the file exists with the same method and maybe work a better solution into RetroPie shell scripts afterward.

OK guys, I solved this one - eventually got the gamepad to connect via usb by trying different ports. Wouldn't work with the bluetooth dongle plugged in, but did without. Then plugged the dongle in, and searched for devices - was able to pair with the plugged in snes30 control (?) and then pair the nes30 control on second attempt. Tried a reset and everything is great!

Strange that it wouldn't let the wired keyboard take me to the gui, but it's done now.

For anyone that wants to disable onboard bluetooth and use a dongle... the above config entry is good.

@Sano Thanks, team!